Storage system

ABSTRACT

The temporary area capacity required to be secured with respect to the whole permanent area is calculated in accordance with the capacity and access frequency of a host computer data permanent area of a disk device contained in the storage system and a disk device of an external storage device that is managed by a storage virtualization function of this storage system. The nonvolatile memory is defined as the temporary area and is used to temporarily store host computer data when a data I/O from the host computer is processed. The required capacity of the temporary area is re-calculated in accordance with an event such as a configuration change in the external storage system.

CROSS-REFERENCE TO PRIOR APPLICATION

This application is a continuation application of U.S. Ser. No.13/216,629, filed Aug. 24, 2011, which is a continuation application ofU.S. Ser. No. 11/968,747, filed Jan. 3, 2008 (now U.S. Pat. No.8,028,146. This application relates to and claims the benefit ofpriority from Japanese Patent Application number 2007-207357, filed onAug. 9, 2007 the entire disclosure of which is incorporated herein byreference.

BACKGROUND

The present invention generally relates to a control method andmanagement method for a storage system that is accessed by a computer ina computer system and, more particularly, to a method for assigningstorage areas of a nonvolatile memory built into the storage system andto a storage area management method.

The information that is handled by businesses and so forth has undergonean explosive increase in keeping with the deregulation of electronicdocument conversion and the conversion of procedures to electronicdocument format, as well as the increase in Internet business. Inaddition to an increase in such information, the amount of data storedin storage devices is increasing rapidly and leading to an increase inthe scale of storage systems as a result of rising customer demand forthe long-term archiving of recordings of corporate activities(transaction information and mail and so forth) in the form of databackups from one disk device to another disk device (Disk-to-DiskBackup) and audit handling.

Accordingly, there is a demand for simplification and increasedefficiencies in the management of complex IT infrastructures at the sametime as increased storage for the respective departments/respectivesystems in business information systems. In particular, expectationshave increased for simplifying the management of storage devices andoptimizing the total costs by using optimal storage in accordance withthe value of data.

One method for reducing the management costs of large-scale storagesystems includes the storage virtualization technology as disclosed inJapanese Application Laid Open No. 2005-11277. Japanese Application LaidOpen No. 2005-11277 discloses a storage virtualization technology(referred to as an ‘external storage connection method’ hereinbelow)that connects a first storage system to one or more second storagesystems and provides a higher level such as a host with a device (calleda ‘logical device’ hereinbelow) that is provided to the host or the likeby a second storage system as a logical device of the first storagesystem via the first storage system. When the first storage systemreceives an I/O request with respect to the logical device from thehost, it is judged whether the access target device corresponds toeither a logical device of the second storage system or a physicaldevice such as a disk device in the first storage system and I/Orequests are distributed to suitable access destinations in accordancewith the result of this judgment.

In addition, one method for simplifying the storage system designincludes a volume management technology that is capable of dynamiccapacity expansion of the kind disclosed in Japanese Application LaidOpen No. 2003-15915 (A volume capacity of which is expanded dynamicallycalled an expansion volume hereinbelow). In Japanese Application LaidOpen No. 2003-15915, during the definition of a logical device, a poolarea is provided in a storage system instead of assigning a fixedphysical storage area (HDD or the like) corresponding to a devicecapacity that is requested by the user and, when update access has beenmade to the logical device, a physical storage area of a prescribedamount is dynamically added from the pool area corresponding to theupdated part. As a result, a large-capacity logical device can beintroduced using a small physical storage area and the storage capacitydesign can be simplified.

On the other hand, as one method for reducing the introduction andrunning costs of a large-scale storage system that stores a large amountof data of the kind mentioned hereinabove, the storage mountingtechnology that adopts a nonvolatile memory such as the flash memorydisclosed in Japanese Patent No. 3507132 may be considered. JapanesePatent No. 3507132 discloses measures against write failure in the eventof an increase in the number of rewrites which is a drawback of flashmemory. A storage system that has a built-in nonvolatile memory such asflash memory instead of or in addition to a HDD and stores data whichare written to or read from the nonvolatile memory by a host by usingthe technology of Japanese Patent No. 3507132 may be considered. Astorage device that combines an increase in the I/O processing speedwith a reduction in the power consumed in comparison with a storagedevice that contains a disk device by storing host data in a nonvolatilememory can be provided. As a result, miniaturization of the systemintroduced and a reduction in the system running costs (the amount ofpower consumption) can be implemented. Flash memory, which constitutesthe current mainstream form of nonvolatile memory, possesses low I/Operformance in comparison with DRAM or S-RAM which are used for the mainmemory of computers. Furthermore, flash memory also possesses low inputperformance in comparison with HDD. Furthermore, flash memory alsopossesses the characteristic of adversely affecting user convenience(e.g. write count restrictions and so forth), hence, flash memory isadopted as a secondary storage device to substitute disk devices and soforth.

The first storage system shown in Japanese Application Laid Open No.2005-11277 must contain a cache memory for the I/O processing of thesecond storage system which is an external storage system. Cache memorytemporarily stores read or write target data when I/O processing isperformed with respect to a disk device that the storage systemcontains, implements high-speed read and write processing using cachehits and is built into almost all storage systems. In thisspecification, a storage area that temporarily stores data as per cachememory is called a ‘temporary area’ and a storage area constituting thefinal storage destination for data as per a disk device is called as a‘permanent area’.

In order to execute high-speed I/O with respect to an external storagesystem, a cache memory (temporary area) of the capacity required for I/Oprocessing must be assigned to I/O processing in accordance with thecapacity of the external storage system and access characteristic(locality) thereof.

Conventionally, a memory device such as a DRAM or SRAM has been adoptedas the cache memory (temporary area) and has contributed towardincreased storage system speeds as a storage medium that possessescompletely different characteristics from a disk device (permanentarea), which is termed ‘high cost, high-speed, and small capacity’.Conversely, in addition to a built-in disk device (permanent area) inthe above first storage system, the inclusion of a memory device as atemporary area used for an external storage system (and an internalbuilt-in disk device) in order to respond to the characteristicsrequired of a temporary area has not been possible.

However, in cases where the first storage system comprising externalstorage connection means is a storage system that uses a nonvolatilememory as the permanent area, a nonvolatile memory can be used as atemporary area of the external storage in the same way as a permanentarea. By using a nonvolatile memory as a temporary area or a permanentarea, there is no longer a need to mount both a disk device and memorytogether and the hardware is simplified, whereby a reduction in hardwarecosts is possible. However, in this implementation, a managementtechnology that is capable of determining and managing the capacity andlocations of the temporary and permanent areas assigned in thenonvolatile memory is required in the implementation. In addition, achange to the temporary area assignment that satisfies the IO processingrequirements of the external storage in accordance with an addition toor reduction in the external storage system as well as changes to theaccess characteristics is required.

In addition, in the next-generation nonvolatile memories such as MRAMand PRAM for which research is progressing as a future technology, theimplementation of a high-speed characteristic that rivals that of DRAMor the like and the elimination of write limitations is planned and anew architecture will be necessary at the time such a new nonvolatilememory is introduced.

SUMMARY

An object of the present invention is to permit, in a storage systemthat comprises external storage connection means and comprises a storagesystem that contains a nonvolatile memory as a permanent area and anexternal storage system, the determination of a temporary area capacitythat meets the I/O processing requirements of the external storagesystem, as well as the selection of assigned areas.

The management server and storage system determine the capacity of atemporary area that is assigned to a nonvolatile memory contained in astorage system, that is, the capacity of a storage area that stores datatemporarily during data inputs and outputs from the host, in accordancewith instructions from the user or an application program and changes tothe configuration such as an addition to or reduction in the storagedevices and assigns the temporary area to a specified area of thenonvolatile memory.

In addition, the capacity of the temporary area assigned to thenonvolatile memory is increased or reduced in accordance with changes inthe capacities of data permanent areas such as disk devices ornonvolatile memory, that is, of storage areas that store host data andin accordance with changes to the access characteristics of such areas.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of the hardware configuration of a computersystem;

FIG. 2 shows an example of the software configuration of the storagesystem;

FIG. 3 shows an example of logical device management information;

FIG. 4 shows an example of LU path management information;

FIG. 5 shows an example of physical device management information;

FIG. 6 shows an example of external device management information;

FIG. 7 shows an example of expansion volume management information;

FIG. 8 shows an example of pool volume management information;

FIG. 9 shows an example of the process flow of temporary area definitioninstruction processing 243 which is executed by a management server 110according to a first embodiment;

FIG. 10 shows an example of the process flow of temporary areadefinition processing 224 that is executed by a storage system 130according to the first embodiment;

FIG. 11 shows an example of the process flow of physical devicedefinition processing 226 which is executed by the storage system 130according to the first embodiment;

FIG. 12 shows an example of the process flow of device definitioninstruction processing 241 that is executed by the management server 110according to the first embodiment;

FIG. 13 shows an example of the process flow of device definitionprocessing 222 which is executed by the storage system 130 according tothe first embodiment;

FIG. 14 shows an example of the process flow of temporary area changeinstruction processing 244 which is executed by the management server110 according to a second embodiment;

FIG. 15 shows an example of the process flow of temporary areaassignment cancellation processing 225 which is executed by the storage130 according to the second embodiment;

FIG. 16 shows an example of the process flow of device migrationprocessing 223 which is executed by the storage system 130 according tothe second embodiment;

FIG. 17 shows an example of the process flow of physical devicedefinition cancellation processing 227 which is executed by the storagesystem 130 according to the second embodiment;

FIG. 18 shows an example of the process flow of the device migrationinstruction processing 242 which is executed by the management server110 according to the second embodiment;

FIG. 19 shows an example of the process flow of I/O processing 221 whichis executed by the storage system 130 according to the first and secondembodiments;

FIG. 20 shows an example of the configuration of a nonvolatile memory134 that is contained in the storage system 130 according to the firstand second embodiments;

FIG. 21 shows an example of an address conversion table held by themanagement server according to the second embodiment;

FIG. 22 shows an example of file collection information that iscollected by the host computer 100 according to the second embodiment;and

FIG. 23 shows an example of the hardware configuration of a computersystem in a modified example which is common to the first and secondembodiments.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Preferred embodiments of the present invention will be describedhereinbelow.

First and second embodiments will be described as embodiments of thecomputer system of the present invention and the storage and devicecontrol methods of the present invention.

The first embodiment is a computer system in which a host computer, afirst storage system, a second storage system that is connected betweenthe host computer and the first storage system, and a management serverare connected via a network, wherein the second storage system containsa nonvolatile memory as a permanent area and contains a storagevirtualization function that permits virtual integration of a device ofanother storage system as its own device, and the management server andsecond storage system determine the capacity of the temporary area inaccordance with an instruction from the user or from an application, andsecures and assigns a temporary area of this capacity in the nonvolatilememory. The device definition processing and I/O processing of thepresent invention will also be described.

Using the same configuration as the first embodiment, the secondembodiment calculates the temporary area capacity that needs to beassigned in accordance with the capacities and access characteristics ofthe disk devices contained in the first storage device and secondstorage system and the capacity and access characteristic of thepermanent area in the nonvolatile memory and performs control toincrease or reduce the required temporary area assignment amount inaccordance with the result of a comparison with the existing assignmentamount. The device migration instruction processing of the presentinvention will also be described.

First Embodiment

The first embodiment will first be described with reference to FIGS. 1to 13 and FIGS. 19 and 20. FIG. 1 shows an example of the hardwareconfiguration of a computer system to which the first embodiment of thepresent invention is applied.

The computer system comprises one or more host computers 100, amanagement server 110, a fibre channel switch 120, a storage system 130,a management terminal 140, and external storage systems 150 a and 150 b(generically referred to as the external storage systems 150). The host100, storage system 130, and external storage systems 150 are connectedvia ports 107, 131, and 151 respectively to ports 121 of the fibrechannel switch 120. In addition, the host 100, storage system 130,external storage systems 150, and fibre channel switch 120 are connectedvia interface control sections (I/F) 106, 138, 157, and 123 respectivelyto the management server 110 via an IP network 175 and are integrallymanaged by storage management software (not shown) which is operated bythe management server 110. This embodiment takes a form where thestorage system 130 is connected to the management server 110 via themanagement terminal 140 but may also have a configuration where thestorage system 130 is connected directly to an IP network.

The host computer 100 is a computer that comprises a CPU 101 and amemory 102 and so forth and reads software such as an operating systemand application programs which are stored in a storage device 103 suchas a disk device or magneto-optical disk device to the memory 102. Thehost computer 100 affords predetermined functions as a result of the CPU101 reading this software from the memory 102 and executing thesoftware. The host computer 100 comprises an input device 104 such as akeyboard and a mouse and an output device such as a display 105, wherethe input device 104 receives an input from the host administrator orthe like, and the output device outputs information for which an outputinstruction has been issued by the CPU 101. Further, the host computer100 comprises one or more interface control sections 106 for aconnection with the IP network 175 in addition to port 107.

The management server 110 is also a computer comprising a CPU 111 and amemory 112 and reads storage management software which is stored in astorage device 113 such as a disk device or magneto-optical disk deviceto the memory 112. The management server 110 affords predeterminedfunctions such as a function for the operation and maintenancemanagement of the whole computer system as a result of the CPU 111reading the storage management software from the memory 112 andexecuting same. When storage management software is executed by the CPU111, the management server 110 collects configuration information, theresource usage rate, performance monitoring information, and fault logsand so forth from the respective devices in the computer system via IPnetwork 175 from the interface control section 116. The managementserver 110 then outputs the information thus collected to an outputdevice such as a display 115 and presents the storage administrator withthe information. In addition, the management server receives aninstruction from the storage administrator via an input device 114 suchas a keyboard and a mouse and transmits the operation and maintenanceinstruction thus received to the respective devices via the interfacecontrol section 116.

The storage system 130 has a configuration in which one or more ports131, one or more control processors 132, one or more memories 133 eachconnected to the control processors 132, one or more nonvolatilememories 134, one or more control memories 135, one or more ports 136,one or more disk devices 137 which are connected to the respective ports136, and an interface control section 138 are connected via an internallink network.

The control processor 132 specifies an access target device in responseto the I/O request received from port 131 and processes I/O requests forthe disk device 137 to which the device corresponds and for devices inthe external storage system 150. Thereupon, the control processor 132specifies an access target device from the port ID and LUN (Logical UnitNumber) contained in the received I/O request. In this embodiment,although a port that corresponds with the fibre channel interface forwhich SCSI (Small Computer System Interface) serves as the higher levelprotocol is assumed as port 131, the port may also be a port thatcorresponds with another storage connection network interface such as anIP network interface for which SCSI is the higher level protocol (iSCSI,for example), or the like.

The storage system 130 of this embodiment has the following devicehierarchy. First, a storage device array of a plurality of disk devices137 or a plurality of permanent areas of the nonvolatile memory 134 isconstituted. This storage device array is managed as one physical deviceby the control processor 132. In addition, the control processor 132 ofthe present invention directly assigns a logical device to the physicaldevice contained in the storage system 130 (that is, the controlprocessor 132 associates physical devices and logical devices). Thelogical devices are managed within the storage system 130 and thenumbers of the logical devices are managed individually for each storagesystem 130. The logical devices are associated with the LUN assigned tothe respective ports 131 and supplied to the host computer 100 asdevices of the storage system 130. That is, the logical devices of thestorage system 130 are identified by the host computer and the hostcomputer 100 accesses the data stored in the storage system 130 by usingthe LUN of the ports 131 corresponding with the logical devices. In thisspecification, there is an external storage connection method accordingto which the control processor 132 manages the logical devices of theexternal storage systems 150 as external devices and virtualizes same asdevices of the storage system 130. One or more of the external deviceswhich are incorporated by using the external storage connection aredirectly associated with the logical devices of the storage system 130as per the physical devices. The external devices are also individuallymanaged within the respective storage systems 130. Further, in thisembodiment, an expansion volume technology that expands a logicaldevice, that is, a virtual volume management technology that allowsphysical storage areas to be dynamically added and assigned to an updateaccess part can also be applied. In this case, a pool volume is assignedto a physical device or external device and a logical device is assignedto an expansion volume by defining the expansion volume incorrespondence with the pool volume. Here, an expansion volume is avirtual device which uses an expansion volume technology and correspondsone for one with the logical device. A pool volume is a virtual devicethat manages a physical storage area which is assigned dynamically to anexpansion volume. In this specification, for the sake of simplification,a pool volume corresponds with one physical device or external devicebut one pool volume may also be constituted by a plurality of physicaldevices or external devices. In order to implement the device hierarchyabove, the control processor 132 performs processing to manage therelationships between respective devices such as logical devices,expansion volumes, pool volumes, physical devices, disk devices 137,permanent areas of nonvolatile memory 134, external devices, logicaldevices of external storage systems 150, convert an access request for alogical device into an access request for a logical device of the diskdevice 137, the permanent area of the nonvolatile memory 134, or theexternal storage device 150, and transmit the converted access requestto the appropriate device. As mentioned earlier, the storage system 130of this embodiment defines one or a plurality of physical devicesstarting with a plurality of disk devices 137 or a plurality of areas ofthe permanent area of the nonvolatile memory 136 (that is, anassociation is made with one or a plurality of physical devices startingwith a plurality of disk devices 137 or a plurality of areas of thepermanent area of the nonvolatile memory 136, for example) and assignsone logical device or one pool volume to one physical device andprovides same to the host computer 100. However, it is understood thatthe individual disk devices 137 or an area of the permanent area of thenonvolatile memory 136 may also be one physical device and one logicaldevice or one pool volume.

Further, in addition to the I/O processing with respect to the device,the control processor 132 executes various processing to implement datasharing between devices such as data duplication and data repositioning.

In addition, the control processor 132 transmits configurationinformation which is to be presented to the storage administrator to themanagement terminal 140 which is connected via the interface controlsection 138 and implements configuration changes to the storage system130 upon receiving, from the management terminal 140, a maintenance andoperation instruction which is input to the management terminal 140 bythe administrator.

The nonvolatile memory 134 is utilized after being partitioned into atemporary area and permanent area. The temporary area increases theprocessing speed with respect to access requests from the host computer100 and, therefore, data which are read frequently by the disk device137 are pre-stored and write data received from the host computer 100are temporarily stored. In cases where a ‘write-after’ which employs thetemporary area of the nonvolatile memory 134 is performed, that is, incases where, after the write data received from the host computer 100have been stored in the temporary area of the nonvolatile memory 134, aresponse to the write request is sent back to the host computer 100before the write data are actually written to the disk device 137, it isdesirable to increase the availability through duplication in order toincrease the resistance of the nonvolatile memory 134 to medium failurein order to prevent the write data stored in the temporary area of thenonvolatile memory 134 from disappearing prior to being written to thedisk device 137. However, the permanent area is used to ultimately storethe data of the host computer 100 in the same way as the disk device137. Accordingly, for the sake of the bit cost and in order to increasethe speed of the I/O processing performance, the temporary areadesirably has a small capacity but effects high speed access throughsimple duplication and the permanent area provides a storage area whichis accessed at a relatively low speed but which has a large capacity andlow cost by adopting a redundant array configuration such as RAID5 as isthe case for disk device 137. Further, according to the presentinvention, for the sake of simplicity, the permanent area of thenonvolatile memory 134 holds and manages an identification number foreach small area of a prescribed size and a physical device is definedfor the whole of the permanent area.

FIG. 20 shows an embodiment of the nonvolatile memory 134. Thenonvolatile memory 134 contains a plurality of switches 2001 and aplurality of memory packages 2002. The memory packages 2002 contain aplurality of nonvolatile memory modules 2004 and a memory controller2003 that controls access to the memory modules 2004. The memorycontroller 2003 links the switches 2001 and the other components in thestorage system 130 via an internal link network and implements memoryaccess and data transfer.

The control memory 135 stores control information for managing theattributes of the respective devices for implementing the devicehierarchy as well as the relationships between the devices and storescontrol information for managing disk written data or non-written dataheld in the temporary area of the nonvolatile memory 134. When thecontrol information stored in the control memory 135 disappears, thedata stored in the disk device 137 or the permanent area of thenonvolatile memory 134 can no longer be accessed and, therefore, thecontrol memory 135 desirably has a configuration for high availabilitywhere the control memory 135 is made nonvolatile by means of a batterybackup or is duplicated in order to increase the resistance to mediumfailure.

As shown in FIG. 1, the respective parts in the storage system 130 areconnected using an internal link network such that the transmission andreception of data between the respective parts, control information, andconfiguration information is executed. As a result of the internal linknetwork, the control processors 132 are able to share and manageconfiguration information on the storage system 130. The internal linknetwork is desirably also multiplexed from the perspective of increasedavailability.

The management terminal 140 comprises a CPU 142, a memory 143, a storagedevice 144, an interface control section 141 which is connected to thestorage system 130, an interface control section 147 that is connectedto an IP network 175, an input device 145 that accepts inputs from thestorage administrator, and an output device such as a display 146 thatoutputs configuration information and management information on thestorage system 130 to the storage administrator. The CPU 142 reads astorage management program that is stored in the storage device 144 tothe memory 143 and, as a result of executing this program, issuesinstructions to reference the configuration information and change theconfiguration information as well as operation instructions forspecified functions, and constitutes an interface between the storageadministrator or management server 110 and the storage system 130 withrespect to maintenance operations on the storage system 130. The storagesystem 130 may also be connected directly to the management server 110with the management terminal 140 omitted and the storage system 130 mayalso be managed by using management software that runs on the managementserver 110.

The external storage system 150 comprises one or a plurality of ports151 that are connected to ports 131 of the storage system 130 via fibrechannel switch 120, a control processor 152, a memory 153, a disk cache154, one or a plurality of disk devices 156 and one or a plurality ofports 155 which are each connected to the disk devices 156. The controlprocessor 152 processes an I/O request with respect to the disk device156 received from the port 151 by executing a program that is stored inthe memory 153. In this embodiment, the external storage system 150 is astorage system that does not comprise a control memory and has asmaller-scale configuration than the storage system 130 but could alsobe a storage system of the same scale with the same configuration as thestorage system 130.

In this embodiment, because port 131 of the storage system 130 and port151 of the external storage system 150 are connected via the fibrechannel switch 120 as shown in FIG. 1, the zoning of the fibre channelswitch 120 is desirably established so as to suppress direct access fromthe host computer 100 to the external storage systems 150. The port 131and port 151 may also be directly connected via the fibre channel switch120.

The software configuration of the storage system 130 of the embodimentof the present invention will be described next.

FIG. 2 is a software configuration view of an example of the controlmemories of the storage system 130 and management server 110 as well ascontrol information and a program for storage control processing whichare stored in memory.

Configuration management information of the storage system 130 that isstored in the control memory 135 includes logical device managementinformation 201, LU path management information 202, physical devicemanagement information 203, external device management information 204,cache management information 205, nonvolatile memory managementinformation 206, expansion volume management information 207, poolvolume management information 208, and device operation information 209.This information items are stored in the control memory 135 in thisembodiment in order to prevent the disappearance of information. Thiscontrol information can be referenced and updated by the controlprocessor 132, whereupon access via a mutual connection network isrequired. Accordingly, for the sake of improving the processingperformance, a copy of the control information required for theprocessing that is executed by the respective control processors 132 mayalso be saved in the memory 133. Further, configuration information forthe storage system 130 is also transmitted to and saved in the controlterminal 140 and management server 110. In cases where the managementserver 110 or management terminal 140 changes the configuration of thestorage system 130 upon receipt of an instruction from the storagemanagement software or storage administrator or cases where theconfiguration is changed as a result of a fault and the automaticexchange of the respective parts inside the storage system 130, one ofthe control processors 132 updates the configuration information in thecontrol memory 135. Further, the control processor 132 reports the factthat the control information has been updated as a result of theconfiguration change to the other control processor 132, managementterminal 140, and management server 110 via the mutual connectionnetwork and introduces the latest information from the control memory135 to the memory of another part.

In addition, the external storage system 150 saves, in the same way asthe storage system 130, logical device management information 251, LUpath management information 252, physical device management information253, and cache management information 254 in order to perform devicemanagement of the logical devices and physical devices inside its owndevices and to perform data management. This content is used with thesame objective as the same name information of the storage system 130.

In addition, the management server 110 saves a copy of the devicemanagement information that is collected from the storage system 130 andexternal storage system 150 and storage management information 232 thatrepresents the attributes of the respective storage systems in thememory 112. This information may also be saved in the storage device 113contained in the management server 110 in order to avoid data loss.

The respective management information will be described next. First,logical device management information 201 will be described. FIG. 3shows an example of logical device management information 201. Thelogical device management information 201 holds an information set thatextends from a logical device number 301 to a data migration in progressflag 310 for each logical device. The logical device number 301 storesnumbers assigned by the control processor 132 to the logical devices inorder to identify the logical devices. Size 302 stores the capacity ofthe logical devices specified by the logical device number 301. Thecorresponding lower-level device number 303 stores the number of thephysical device, external device, or expansion volume that is associatedwith the logical device, that is, the entry number of the physicaldevice management information 203, external device managementinformation 204, or expansion volume management information 207 whichare respective management information. Although a logical device andphysical device/external device/expansion volume correspond one for onein this embodiment, in cases where one logical device is formed bylinking a plurality of physical devices or external devices, the logicaldevice management information 201 requires a physical/external devicenumber list to which the respective logical devices correspond and anentry for storing the number of logical devices. In cases where thelogical devices are undefined, an invalid value is set for thecorresponding lower-level device number 303. Type 304 stores device typeidentification information on the logical devices. The storage system130 can define logical devices of a plurality of different device typessuch as data management units in the cache as well as the storage formatof device management information (the existence of managementinformation storage with respect to the disk space and the storageformat, and so forth) and the particular device types of the respectivelogical devices are held by type 304.

Information indicating the logical device state is set for the devicestate 305. The states ‘attached’, ‘detached’, ‘undefined’, and ‘blocked’exist. ‘Attached’ indicates a state where the logical device is workingnormally, an LU path has been defined for one or more ports 131, and thelogical device can be accessed by the host computer 100. ‘Detached’indicates a state where the logical device has been defined and isworking normally but, since the LU path is undefined, same cannot beaccessed by the host computer 100. ‘Unmounted’ indicates a state wherethe logical device has not been defined for a physical device orexternal device or expansion volume and cannot be accessed by the hostcomputer 100. ‘Blocked’ indicates a state where a fault occurs in thelogical device and cannot be accessed by the host computer 100. Theinitial value of the device state 305 is ‘unmounted’ and is changed to‘detached’ as a result of logical device definition processing andchanged to ‘attached’ as a result of LU path definition processing.

For the port number of entry 307, information indicating which port ofthe plurality of ports 131 has its LUN defined for the logical device,that is, identification information identifying the port 131 that isused in order to access the logical device are set. Here, identificationinformation of the port 131 constitutes unique numbers in the storagesystem 130 that are assigned to the respective ports 131. In addition,the target ID and LUN stored in the same entry 307 are identifiersserving to identify the logical devices. In this embodiment, theidentifiers serving to identify the logical devices which are usedinclude an SCSI-ID and LUN which are used in cases where the device isaccessed by the host computer 100 using SCSI. The entry 307 hasinformation set when the LU path definition for the logical device isexecuted. The connected host name 308 is a host name that identifies thehost computer 100 which has been granted access to the logical device.Any value may be employed as the host name so long as the value is avalue that makes it possible to uniquely identify the host computer 100or port 107 such as a WWN (World Wide Name) that is assigned to the port107 of the host computer 100. The same storage system 130 holdsmanagement information relating to the port attributes such as the WWNof each port 131. The entry 308 is established by the storageadministrator during logical device definition. The number of thelower-level device being transferred 308 stores the migrationdestination device number in cases where the logical device is beingtransferred from an existing physical device/external device/expansionvolume to another physical device/external device/expansion volume. Incases where the logical device is undergoing data migration, ‘ON’ isstored in data migration in progress flag 310 and address informationindicating the final area in which data migration is completed is storedin a data migration progress pointer 309. The entries 308 and 309 arevalid only when the data migration in progress flag 310 is ‘ON’.

Secondly, the LU path management information 202 will be described. FIG.4 is an example of LU path management information 202. The LU pathmanagement information 202 holds information corresponding to valid LUNthat have been defined for the respective ports for the respective ports131 in the storage system 130. The entry of the target ID/LUN402 storesthe LUN defined for (assigned to) the ports 131. Corresponding logicaldevice number 403 stores the number of the logical device to which theLUN is assigned. The connected host name 404 stores informationindicating the host computer 100 that has been granted access to the LUNdefined for the port 131 and the WWN assigned to the port 107 of thehost computer 100, for example, is used as information representing thehost computer 100. There are cases where the LUN of a plurality of ports131 are defined for (assigned to) one logical device and the logicaldevice can be accessed by a plurality of ports 131. In this case, thesum of sets of the connected host name 404 of the LU path managementinformation 202 relating to the respective LUN of the plurality of ports131 is held for the connected host name 308 of the logical devicemanagement information 201 relating to the logical devices.

Thirdly, the physical device management information 203 will bedescribed. The physical device management information 203 is used in themanagement of physical devices which are constituted by one or more diskdevices 137 in the storage system 130 or one or more areas of thepermanent area of the nonvolatile memory 134. FIG. 5 is an example ofthe physical device management information 203. The respective storagesystems 130 hold information sets from the physical device number 501 tothe disk/memory internal size and an offset 507 for each physical devicethat is present in its own device. The physical device number 501registers an identification number for identifying a physical device.Size 502 stores the capacity of the physical device specified by thephysical device number 501. The logical device or pool volume numberwith which the physical device is associated is stored in the event thatthe logical device or pool volume has been defined as the correspondinghigher-level device number 503. In cases where the physical device hasnot been assigned to a logical device or pool volume, an invalid valueis set for entry 503. The device state 504 has information indicatingthe state of the physical device set for device state 504. The states‘attached’, ‘detached’, ‘unmounted’, and ‘blocked’ exist. ‘Attached’indicates a state where the physical device is working normally and hasbeen assigned to a logical device or pool volume. ‘Detached’ indicates astate where the physical device has been defined and is working normallybut has not been assigned to a logical device or pool volume.‘Unmounted’ indicates a state where the physical device of the physicaldevice number has not been defined on the disk device 137. ‘Blocked’indicates a state where a fault has occurred with the physical deviceand same cannot be accessed. The initial value of the device state 504is ‘unmounted’, which is changed to ‘detached’ as a result of physicaldevice definition processing and to ‘attached’ in the event that thelogical device is defined. RAID configuration 505 holds informationrelating to the RAID configuration such as the RAID level of the diskdevice 137 or permanent area of the nonvolatile memory 134 to which thephysical device has been assigned, the numbers of data diskdevices/memory areas and parity disk devices/memory areas and the sizeof the stripes which are the data partition units. Disk/memory numberlist 506 holds the respective identification numbers of the plurality ofdisk devices 137 or the plurality of areas of the permanent area of thenonvolatile memory 134 constituting the RAID to which the physicaldevice has been assigned. The identification numbers of the plurality ofareas of the disk device 137 and the permanent area of the nonvolatilememory 134 are unique values assigned in order to identify the diskdevices 137 and the plurality of areas of the permanent area of thenonvolatile memory 134 in the storage system 130. The disk/memoryinternal size/offset 507 is information indicating which area in eachdisk device 137 or specified area of the permanent area of thenonvolatile memory 134 the physical device is assigned to. In thisembodiment, for the sake of simplification, all the physical deviceshave the same offset and size in each disk device 137 or specified areaof the permanent area of the nonvolatile memory 134 which constitute theRAID.

Fourthly, the external device management information 204 will bedescribed. The external device management information 204 is used inorder to manage logical devices of the external storage systems 150connected to the storage system 130 as external devices. FIG. 6 is anexample of the external device management information 204. The storagesystem 130 holds information sets from the external device number 601 tothe target port ID/target ID/LUN list 608 for each external devicemanaged by the storage system 130. The external device number 601 storesa unique value in the storage system 130 that the control processor 132of the storage system 130 has assigned to the external device. The size602 stores the capacity of the external device specified by the externaldevice number 601. The corresponding higher-level device number 603registers the number of the logical device or pool volume in the storagesystem 130 with which the external device is associated. As per thedevice state 504 of the physical device management information 203, thestate of the external device is set for the device state 604. Thestorage system 130 is not connected to the external storage system 150in its initial state and, therefore, the initial value of the devicestate 604 is ‘unmounted’. The storage identification information 605holds identification information for the external storage systems 150constituting the external device. Identification information that may beconsidered includes a combination of vendor identification informationfor the same storage system and manufacturing serial numbers to whichthe respective vendors are uniquely assigned, and so forth. The externalstorage internal device number 606 stores the identification numberassigned within the external storage system 150 to the logical device ofthe external storage system 150 that corresponds with the externaldevice, that is, the logical device number. The initiator port numberlist 607 registers the identification number of the port 131 of thestorage system 130 that permits access to the external device. In caseswhere the external device can be accessed from a plurality of ports 131,a plurality of port identification numbers are registered. The targetport ID/target ID/LUN list 608 holds the port IDs of the ports 151 andone or a plurality of target ID/LUN to which the external device isassigned in cases where the LUN of one or more ports 151 of the externalstorage system 150 are defined for external device. In cases where thecontrol processor 132 of the storage system 130 accesses an externaldevice (in cases where the control processor transmits an I/O request tothe external device from ports 131), the target ID and LUN assigned tothe external device is used by the external storage system 150 to whichthe external device belongs as information for identifying the externaldevice.

Fifthly, the expansion volume management information 207 will bedescribed. In this embodiment, an expansion volume is a virtual volumeto which a physical storage area is not assigned when the expansionvolume is defined and which dynamically adds and assigns a storage areaof the pool volume as a physical storage area that corresponds to theaccess part in accordance with update access by the host computer or thelike. This information is used to manage the relationship between theexpansion volume and the logical device and pool volume.

FIG. 7 is an example of the expansion volume management information 207.The storage system 130 holds an information set from an expansion volumenumber 701 to a real area assignment total 707 for each of the expansionvolumes. The expansion volume number 701 stores a unique value in thestorage system 130 that has been assigned to the expansion volume by thecontrol processor 132 of the storage system 130. Size 702 stores theapparent capacity from the host computer of the expansion volumespecified by the expansion volume number 701. The corresponding logicaldevice number 703 registers the number of the logical device in thestorage system 130 with which the expansion volume is associated. Thestate of the expansion volume is set for the volume state 704 as per thesame name information of the physical device management information 203.The initial value of the volume state 704 is ‘unmounted’ in thisembodiment. The corresponding pool number list 705 holds the numbers ofall the pool volumes that store the physical storage areas of theexpansion volume. The pool entry correspondence management information706 stores information indicating the correspondence between the storagespace that the expansion volume provides for the host computer andphysical storage area in the corresponding pool volume. In an initialstate where only the expansion volume has been defined, a physicalstorage area has not been assigned to the volume. Hence, the wholestorage area of the volume is in an unassigned state. When update accessto the logical device corresponding to the expansion volume is made bythe host computer or the like, the access target position in theexpansion volume is calculated and a check is made of whether a poolvolume storage area has been assigned to the relevant storage areaentry. In cases where a physical storage area has not been assigned tothe access target storage area, a suitable storage area is selected fromone or more pool volumes indicated by the corresponding pool number list705 and assigned as a physical storage area of the access target area ofthe expansion volume. The final real area assignment total 707 storesthe total amount of physical storage area assigned to the expansionvolume.

Sixthly, the pool volume management information 208 will be described.According to the present invention, the pool volume is a virtual volumethat provides and manages a storage area that is assigned as thephysical storage area of an expansion volume. This information is usedto manage the relationship between the pool volume and the expansionvolume and physical/external device.

FIG. 8 shows an example of the pool volume management information 208.The storage system 130 holds an information set from a pool volumenumber 801 to a corresponding expansion volume number list 808 for allof the pool volumes. The pool volume number 801 stores a unique value inthe storage system 130 that has been assigned to the pool volume by thecontrol processor 132 of the storage system 130. The size 802 stores thecapacity of the pool volume specified by the pool volume number 801 andspare capacity 803 stores the total of the storage area that has notbeen assigned to an expansion volume. The state of the pool volume isset for the volume state 804 in the same way as the same nameinformation of the expansion volume management information 207. Thephysical/external device number 805 holds the number of thephysical/external device to which the pool volume is assigned. The poolentry size 806 stores information that indicates the size of the unit(entry) assigned when the storage area of the pool volume is assigned asthe physical storage area of the expansion volume. The storage area ofthe expansion storage area is partitioned into a plurality of entries inthe entry size of the corresponding pool volume and the state ofcorrespondence between the respective entries of the expansion volumeand the respective entries of the pool volume is held as the pool entryassignment state management information 807. The corresponding expansionvolume number list 808 holds the numbers of one or more expansionvolumes to which the storage area of the pool volume has been assignedas a physical storage area.

Seventhly, the device operation information 209 will be described. Inthis embodiment, the I/O frequency and the locality and continuity ofthe data length or access range and so forth is collected from the hostcomputer 100 for each logical device. The required amount of cachememory of the physical device or external device which corresponds witheach logical device, that is, the required amount of the temporary areaof the nonvolatile memory 134 is calculated on the basis of thisinformation.

In this embodiment, the storage system 130 manages the devices/volumesby using the seven device/volume management information items above. Inthe initial state of the storage system 130, physical devices arealready defined upon shipping from the factory for the respective diskdevices 137 and the permanent area of the nonvolatile memory 134 and thelogical device, external device, expansion volume, and pool volume areeach undefined. In addition, the user or storage administrator definesthe logical devices of the external storage system. 150, which areconnected to the same storage system 130 when the storage system 130 isintroduced, as external devices, defines logical devices and poolvolumes in the physical devices and external devices and, in the case ofpool volumes, further defines expansion volumes and logical devices anddefines LUNs for the respective ports 131 for the logical devices.

In addition, the storage system 130 saves the nonvolatile memorymanagement information 206 and cache management information 205 to thecontrol memory 135 in order to manage the nonvolatile memory 134 and thetemporary area assigned to the nonvolatile memory 134. The managementinformation for the nonvolatile memory 134 saves the assignment statusof the respective areas of the memory space provided by the built-innonvolatile memory 134, that is, information indicating which of thetemporary area or permanent area has been assigned or not assigned. Thecache management information 205 is constituted by area managementinformation for the temporary area of the nonvolatile memory 134 and hitor miss judgment information that indicates which of the data in theaddress space of the physical device or external device are stored inwhich temporary areas. As a method of managing temporary areas, forexample, a method that involves partitioning the temporary area intosmall areas (segments) of a prescribed size, holding information on thecorrespondence between the address spaces of the physical device orexternal device and each segment, and information indicating whether theinformation held by each segment is not written by the device (dirty) orwritten (clean) may be considered.

Thereafter, returning once again to FIG. 2, programs that are stored inthe memory 133, 153, and 112 of storage system 130, external storagesystems 150 and management server 110 respectively will be described. Inaddition to storing a copy of the control information, each memorystores a program that is operated by the control processors 132 and 152and the CPU 111 in the respective parts.

In this embodiment, processing to assign a temporary area of thenonvolatile memory 134 of the storage system 130, processing to assign aphysical device which is associated with this processing, and processingto define a device will be described. In addition, according to thesecond embodiment (described subsequently), processing to change theassignment of the temporary area and device migration processing whichis associated with this processing will be described. This processing isexecuted in response to a request from the user or from an applicationas a result of co-operation between the management server 110, storagesystem 130, and external storage systems 150.

First, in correspondence with the temporary area assignment processingof the nonvolatile memory 134, the temporary area definition instructionprocessing 243 by the management server 110 is stored to the memory 112,and the temporary area assignment processing 224 and physical devicedefinition processing 226 by the storage system 130 are stored to thememory 133.

FIG. 9 shows an example of the process flow of temporary area definitioninstruction processing 243 which is executed by management server 110.The management server 110 calculates the capacity of a temporary areathat must be assigned to the nonvolatile memory 134 of the storagesystem 130 on the basis of the information in the copy 231 of the devicemanagement information (step 901). More specifically, the managementserver 110 calculates the capacity of the physical/external device fromthe physical device management information 203 and external devicemanagement information 204, obtains the access attributes (frequency andlocality, and so forth) of the physical/external devices that correspondwith the respective logical devices from the device managementinformation 209, and calculates the required amount of temporary area onthe basis of the access attributes. For example, a method that involvesestimating the cache hit improvement rate with respect to the temporaryarea assignment capacity from the access frequency and locality andexercising control so that the performance expected of the respectivelogical devices is achieved may be considered. A variety of algorithmsexist for the calculation of the capacity of the temporary area. If thetemporary area required amount is calculated on the basis of a specifiedalgorithm, an instruction to assign a temporary area to the nonvolatilememory 134 is issued to the storage system 130 (step 902). Once theassignment of a temporary area is complete, the amount and proportion ofthe area of the nonvolatile memory 134 that has not been assigned as thetemporary area or permanent area (called an ‘unassigned area’hereinbelow) is then calculated and, in cases where the amount andproportion exceed a prescribed level, an instruction is issued to thestorage system 130 to define the physical device by defining theexcessive nonvolatile memory 134 as the permanent area (step 903). As aresult, the excessive nonvolatile memory 134 is included as a sparedevice that is managed by the storage system 130 as a physical device.

FIG. 10 shows an example of the process flow of temporary areaassignment processing 224 that is executed by the storage system 130.The control processor 132 of the storage system 130 which receives thetemporary area assignment instruction from the management server 110selects the unassigned area of the nonvolatile memory 134 correspondingwith the instructed capacity on the basis of the nonvolatile memorymanagement information 206 and changes the unassigned area to thetemporary area (steps 1001, 1002). In addition, the newly assignedtemporary area is registered in the cache management information 205 soas to be managed partitioned into segments (step 1003). Here, thecontrol processor 132 performs registration with respect to the controlmemory 135. The control processor 132 also performs registration withrespect to the memory 133 in cases where the memory 133 also has cachemanagement information 205.

FIG. 11 shows an example of the process flow of physical devicedefinition processing 226 which is executed by the storage system 130.The control processor 132 of the storage system 130 that receives thephysical device definition instruction with respect to an unassignedarea of the nonvolatile memory 134 from the management server 110selects an unassigned area of the nonvolatile memory 134 of a capacitythat corresponds to the instruction on the basis of the nonvolatilememory management information 206 and changes the unassigned area to apermanent area (steps 1101, 1102). In addition, the control processor132 sets the physical device management information 203 so that aphysical device is defined for the newly assigned permanent area. Morespecifically, the control processor 132 registers the size of thepermanent area defining the physical device, the identification numberof the permanent area, and the offset and size in each area for thephysical device management information 203 that corresponds with thespecified physical device.

As described hereinabove, the temporary area of the nonvolatile memory130 is defined as a result of the co-operation between the managementserver 110 and storage system 130. The logical device definitionprocessing and the I/O processing will be described next as examples ofnormal processing that accompanies storage operation management in sucha system environment.

First, in correspondence with the logical device definition processing,the device definition instruction processing 241 by the managementserver 110 is stored to the memory 112 and the device definitionprocessing 222 by the storage system 130 is stored to the memory 133.

FIG. 12 shows an example of the process flow of device definitioninstruction processing 241 that is executed by the management server110. The management server 110 receives a logical device definitionrequest of the storage system 130 from the user or an applicationprogram via an IP network 175 and interface control section 116 (step1201). Information contained in the request that may be consideredincludes, for example, identification information on the storage system.130, the logical device number, access source HBA specificationinformation (WWN or the like), port specification information (port IDsof the port 131, target IDs, a list of LUN and so forth), deviceattribute information (normal volume/expansion volume, applications, andso forth). The management server 110 first confirms, based on thisinformation, that the request is from a user or an application programin the host computer 100 with management access rights to the storagesystem 130 based on the management access rights settings set for thestorage system 130 and judges the feasibility of executing this request.Thereafter, the management server 110 judges whether the logical deviceis to be defined as a normal volume or defined as an expansion volumefrom the information contained in the device definition instruction(step 1202). In cases where the logical device has been assigned as anexpansion volume, the management server 110 defines the expansion volumethat corresponds with one of the already defined pool volumes if theremaining capacity of all of the pool volumes corresponding with thephysical/external device, that is, the total capacity of the areas thathave not been assigned as the physical storage area of the expansionvolume is equal to or more than a prescribed value, and instructs thestorage system 130 to assign the logical device to the expansion volume(steps 1203, 1204). If the capacity is inadequate, the management server110 checks among the physical/external devices for devices that have notbeen assigned to a logical device or pool volume (‘spare devices’hereinbelow), defining a new pool volume and expansion volume if such adevice exists and issuing an instruction to the storage system 130 toassign the logical device (step 1205). If no spare device exists, themanagement server 110 reports an error with the logical devicedefinition processing to the source of the request (step 1208). However,in cases where the logical device is not to be defined as an expansionvolume but, rather, to be defined as a normal volume in the judgment ofstep 1202, a spare physical/external device is sought and the assignmenttarget device is determined and an instruction for the assignment of thelogical device to the assignment target device is issued to the storagesystem 130 (step 1206). After issuing the instruction to the storagesystem 130, the management server 110 sends a completion report to thesource of the request (step 1207).

FIG. 13 shows an example of the process flow of device definitionprocessing 222 which is executed by the storage system 130. First, thestorage system 130 receives a logical device definition request from themanagement server 110 (step 1301). Thereupon, the management server 110transmits a logical device definition to the storage system 130 via theIP network 175 and management terminal 140. The control processor 132stores the request in the control memory 135. In addition to theinformation that the management server 110 receives in the devicedefinition instruction processing 241, the information contained in therequest may include, in the case of a normal volume, the logical deviceassignment target physical device or external device number or the like.However, in the case of an expansion volume, the information containedin the request may include the newly assigned expansion volume numberand the expansion volume assignment target pool volume number or thenewly assigned expansion volume number/pool volume number and the poolvolume assignment target physical device or external device number. Incases where the logical device is an expansion volume, the controlprocessor 132 defines a pool volume for the designated physical deviceor external device if necessary (steps 1302, 1303, 1304), and defines anexpansion volume for the pool volume (step 1305). Here, as a pool volumedefinition, more specifically, the control processor 132 sets, for theinformation entry corresponding with the designated pool volume number,the physical device number or the external device number of theassignment target as the physical device number or external devicenumber 805, sets size 802 by referencing the management information forthis device, and initializes the spare capacity 803 at the value of size802, the volume state 804 as ‘detached’, and the correspondenceexpansion volume number list 808 as an invalid value. In addition, thecontrol processor 132 may also use a fixed value in the storage system130 for the pool entry size 806 or may set information indicating thissize for the logical device assignment instruction from the user. Thecontrol processor 132 also initializes the pool entry assignment statemanagement information 807 so that all the entries are unassigned to theexpansion volume. In addition, for the expansion volume definition andspecifically for the information entries of the pool volume managementinformation 208 for pool volumes that corresponds with the informationentries of the expansion volume management information 207 correspondingwith the designated expansion volume number, the expansion volume numberis registered in the correspondence expansion volume number list 808 and‘attached’ is registered as the volume state 804. In addition, thecontrol processor 132 sets the size of the logical device correspondingwith the expansion volume as size 702, sets the corresponding logicaldevice number 703 to an invalid value, sets the volume state 704 as‘detached’, sets the stop flag to ‘On’, sets the final activation/stoptime 706 as the current time, sets the corresponding pool number list707 to the pool volume number, and sets the real area assignment totalat 0. The pool entry correspondence management information 708 isinitialized such that all the entries are in an unassigned state.Thereafter, the control processor 132 performs a LUN path definition forthe designated port 131 after defining the logical device for theexpansion volume and reports the completion of processing to themanagement server 110 (steps 1306, 1307). Here, for the logical devicedefinition and, more specifically, for the corresponding logical devicemanagement information 201 and expansion volume management information207, the control processor 132 sets the corresponding logical devicenumber 703 to the logical device number and the volume state 704 to‘attached’. In addition, the size 302 and type 304 are set to theassignment instruction content, the corresponding lower-level devicenumber 303 is set to the expansion volume number, the device state isset to ‘detached’, the entries 306 to 309 are to the invalid values, andthe data migration in progress flag 310 is set to ‘Off’. In addition,for the LUN path definition and, more specifically, for thecorresponding logical device management information 201 and LU pathmanagement information 202, the control processor 132 sets the portinformation and sets the entries 306 and 307 and entries 402 and 404 asthe information on the connected host computer 100 designated by theassignment instruction. In addition, the corresponding logical devicenumber 403 is set to the logical device number. However, in cases wherethe logical device is a normal volume, the logical device is definedwith respect to the designated spare physical device or external deviceand LUN path definition is performed, whereupon the completion ofprocessing is reported (steps 1302, 1306, and 1307). Here, for thelogical device definition, in specific terms, required information isset for the corresponding logical device management information 201,physical device management information 202, or external devicemanagement information 203.

Thereafter, I/O processing 221 involves storage to memory 133 by thestorage system 130 in correspondence with the I/O processing withrespect to the logical device by the host computer.

FIG. 19 shows an example of the process flow of I/O processing 221 whichis executed by the storage system 130. The storage system 130 receivesan I/O request from the host computer 100 (step 1901). The controlprocessor 132 discards the processing depending on the type of I/Orequest (step 1902).

In cases where the control processor 132 judges in step 1902 that therequest is a read request, the control processor 132 judges, based onthe cache management information 205, whether there is a cache hit orcache miss for the read target data (step 1903). In the case of a cachemiss, the cache management information 205 is manipulated and a sparesegment from the temporary area of the nonvolatile memory is assigned(step 1904), whereupon data staged from the disk 137 or external storagesystem 150 which is a physical device are stored in the nonvolatilememory 134 (step 1905) before data are transferred to the host computer(step 1906). In the case of a cache hit, the control processor 132 readsdata from the nonvolatile memory 134.

Furthermore, in step 1902, the control processor 132 discriminates thefact that the I/O request is a write request and discriminates whetherthere is a cache miss (step 1908). In cases where there is a cache miss,the control processor 132 assigns a spare segment (step 1909). Here, acache miss refers to a state where a segment has not been assigned tothe nonvolatile memory 134 for a certain data area of the logicaldevice. Thereafter, after storing write data from the host computer inthe segment (step 1910), the control processor 132 de-stages the data tothe permanent area of the physical device or external device or the like(step 1911). However, in cases where a cache hit is discriminated instep 1908, because a temporary area assigned to the write target dataexists in the nonvolatile memory 134, data are stored at the relevantaddress in that temporary area.

However, in cases where the control processor 132 discriminates that theI/O request is neither a write request nor a read request in step 1902(a sensing command or the like, for example), the control processor 132executes the requested processing (step 1912).

Finally, the control processor 132, which has executed the processing,reports the completion of processing to the host computer 100 and endsthe processing (step 1907).

This embodiment affords the following effects by virtue of the aboveconfiguration. This embodiment is capable of determining the capacity ofthe temporary area in accordance with the configuration of a virtualstorage system and the capacity and access characteristics of thevirtualized device, and is able to utilize a nonvolatile memory as atemporary area or permanent area.

Second Embodiment

In the first embodiment, a method that involved calculating the requiredcapacity of the temporary area from the capacities and accesscharacteristics of a physical device and external device which aremanaged by the storage system 130 and assigning the required temporaryarea was described. In the second embodiment, a method that involvessensing an increase or reduction in external storage systems as well aschanges to the access characteristics with respect to the respectivedevices thereof and then reviewing the temporary area assignment amountwill be described.

The second embodiment will be described using FIGS. 1 to 8 and FIGS. 14and 18. The first and second embodiments have many points in common and,therefore, only the differences between the two embodiments will bementioned.

The software configuration of the second embodiment is shown in FIG. 2as per the first embodiment. In the second embodiment, in correspondencewith the assignment change processing for the temporary area of thenonvolatile memory 134, the temporary area change instruction processing244 by the management server 110 is first stored to memory 112 and thetemporary area assignment cancellation processing 225, device migrationprocessing 223, and physical device definition cancellation processing227 by the storage system 130 are each stored to memory 133.

FIG. 14 shows an example of the process flow of the temporary areachange instruction processing 244 that is executed by the managementserver 110. The CPU 111 of the management server 110 calculates thecapacity of the temporary area that is already assigned to thenonvolatile memory 134 at a certain point in time on the basis of thecache management information 205 and nonvolatile memory managementinformation 206 (step 1401). In addition, using a method like that ofstep 1001 of the temporary area definition instruction processing 224,the required temporary area assignment amount at that point in time iscalculated (step 1402). In cases where these values are compared and thedifference between the two values exceeds a prescribed value, the CPU111 controls the temporary area assignment amount. In cases where thecapacity of the already assigned temporary area of the nonvolatilememory 134 is equal to or more than a prescribed value for the requiredamount (step 1403), the temporary area corresponding to the excesscapacity is selected as a cancellation candidate (step 1408). As amethod of selecting the temporary area, a temporary area including alarge number of unused segments may be selected or a temporary area witha few segments storing dirty data may be selected. The CPU 111 addsinformation specifying the selected area and issues an instruction tothe storage system 130 to cancel the assignment of the specifiedtemporary area (step 1409). Here, only the capacity of the temporaryarea whose assignment needs to be cancelled may be added withoutselecting the temporary area whose assignment is to be cancelled and thetemporary area whose assignment is to be cancelled may be determined bythe storage system 130. Once the assignment of the specified temporaryarea is cancelled, the CPU 111 issues an instruction to the storagesystem 130 to set a permanent area in an unassigned area of thenonvolatile memory 134 and to perform physical device definition (step1410). If the capacity of the already assigned temporary area is smallerthan the prescribed value for the required amount, a physical devicedefined for the nonvolatile memory 134 which corresponds to the excesscapacity is selected and an instruction is sent to the storage system130 to transfer the logical device corresponding with the physicaldevice to the physical device or external device defined for disk device137 (step 1405). Once migration is complete, the CPU 111 issues aninstruction to the storage system 130 to cancel the assignment of thephysical device (step 1406). Once complete, the management server 110issues an instruction to the storage system 130 to assign the unassignedarea as the temporary area (step 1407).

FIG. 15 shows an example of the process flow of temporary areaassignment cancellation processing 225 which is executed by the storage130. The storage system 130 receives a temporary area assignmentcancellation instruction from the management server 110 via themanagement terminal 140. Thereafter, the control processor 132 selectsthe temporary area of the nonvolatile memory 134 constituting theassignment cancellation target if necessary (steps 1501, 1502) and, forthe temporary area constituting the assignment cancellation target,confirms, based on the cache management information 205, the existenceof dirty data, that is, the existence of segments storing host updatedata that are not written in the permanent area. If dirty data exist,the non-written data (dirty data) are de-staged to the correspondingphysical device or external device (step 1503). Once the de-staging ofall the dirty data of the target temporary area is complete, thecorresponding entry for the nonvolatile memory management information206 is changed to show ‘unassigned area’ and all the corresponding cachemanagement information 205 is initialized (step 1504).

FIG. 16 shows an example of the process flow of device migrationprocessing 223 which is executed by the storage system 130 according tothe second embodiment. The control processor 132 cyclically activatesthis processing and checks whether a device migration request has notbeen registered (step 1601). As mentioned earlier, the device migrationrequest is registered when a logical device that corresponds with aphysical device defined as the permanent area is transferred to the diskdevice 137 or external device which is another physical device in orderto expand the temporary area of the nonvolatile memory 134. In addition,as will be described subsequently, the device migration request isregistered when data migration between levels is required based on thedata values or the like in the hierarchical storage of the permanentarea of the nonvolatile memory 134, the disk device 137, and theexternal device which is constructed by the storage system 130. If thedevice migration request has not been registered, this processing isended without being performed (step 1601). In cases where the requesthas been registered, the processing with respect to whether the targetlogical device is an expansion volume or normal volume is discarded(step 1602). In cases where the logical device is a normal device andthe requested processing is transferred to a spare device, the data ofthe migration source logical device is sequentially transferred from theheader address to a migration destination physical device or externaldevice and, once the data migration is complete for all areas, thedevice management information is updated such that the migration sourcelogical device which is mapped to the current corresponding physicaldevice or external device will be mapped to the migration destinationphysical device or external device (steps 1606, 1607). Further, in caseswhere the requested processing is a switch to another logical device,the data of the migration source/migration destination logical device isread in sequence from the header address to another storage device suchas the temporary area of the nonvolatile memory 134 and the data of themigration source logical device are switched to the migrationdestination logical device and the data of the migration destinationlogical device are switched to and written to the migration sourcelogical device. Once the data switching is complete for all the areas ofthe logical device, the device management information is updated so thatthe relationship with the corresponding physical device or externaldevice is switched for the migration source logical device and themigration destination logical device respectively (steps 1604, 1605).

However, in cases where the logical device is an expansion volume, whenthe requested processing is migration processing to another pool volume,the control processor 132 searches for an entry for which a real areahas been assigned in the corresponding expansion volume in sequencestarting from the logical device header entry and adds only the data ofthis entry to the spare entry of the migration destination pool volume.Stated in more detail, the migration destination pool volume is added tothe corresponding pool volume of the expansion volume and data read fromthe entry of the migration source pool volume are written by assigning aspare entry of the migration destination pool volume and managementinformation is updated so that the entry of the migration destinationvolume is mapped to the entry of the expansion volume. This processingis sequentially executed while using a progress pointer for the logicaldevice management information and, once the migration processing iscomplete for all areas, the migration source pool volume is deleted fromthe corresponding pool volume of the expansion volume (the pool volumeto which the logical device corresponds) (steps 1609, 1610). Inaddition, in cases where the requested processing is an instruction toswitch to another logical device, the control processor 132 sequentiallysearches for an entry for which a real area (pool volume entry) has beenassigned starting with the header entry of the migrationsource/migration destination logical device and transfers the data ofthe entry by newly assigning a spare entry of a partner pool volume forthe target entry. In the migration processing step, when there is alarge difference in the number of migration execution entries betweenthe migration destination/migration source logical devices, there is arisk that the number of spare entries of the first pool volume will beexhausted. Hence, the progress must be controlled so that there is not alarge difference in the numbers of migration execution entries betweenthe migration destination/migration source logical devices. Once theswitch processing of all areas has been completed in this manner, thedevice management information is updated such that the correspondencebetween the respective pool volumes of the migrationdestination/migration source logical devices is switched (steps 1611 to1616).

FIG. 17 shows an example of the process flow of physical devicedefinition cancellation processing 227 which is executed by the storagesystem 130. The control processor 132 initializes the physical devicemanagement information 203 corresponding with the designated physicaldevice and cancels the correspondence between the permanent areaestablished in the nonvolatile memory 134 and the unassigned area (step1701). Thereafter, the nonvolatile memory management information 206 isupdated so that the permanent area of the nonvolatile memory 134 is anunassigned area, whereupon the processing is ended (step 1702).

As described hereinabove, the temporary area assignment state of thenonvolatile memory 134 is changed as a result of the co-operationbetween the management server 110 and storage system 130. Logical devicemigration processing will be described next as an example of normalprocessing that accompanies the storage operation management in such asystem environment.

In correspondence with the logical device migration processing, thedevice migration instruction processing 242 by the management server 110is stored to memory 112 and the device migration processing 223 by thestorage system 130 is stored to memory 133. Of these processes, thedevice migration instruction processing 242 that has not yet beendescribed will be described next.

FIG. 18 shows an example of the process flow of the device migrationinstruction processing 242 which is executed by the management server110. The management server 110 judges whether it is necessary to switchfrom within a logical device to another logical device that correspondswith another physical device or external device (step 1801). Morespecifically, as per DLCM (data life cycle management), data positioningbetween devices is reconsidered to establish a more preferable datapositioning between the respective levels of the hierarchical storagemanaged by the storage system 130 on the basis of the value of the datastored in the respective logical devices and the access frequency anddata protection term and so forth. In cases where, as a result of thejudgment, a device for which switching is required exists (step 1802),the management server 110 issues an instruction to the storage system130 to perform device switching in which information specifying themigration source and migration destination devices is added (step 1803),introduces the latest information on the device at the point where theswitching is complete from the storage system 130 to the memory 112 andupdates the copy 231 of the device management information (step 1804).

In step 1801, for example, when data positioning is performed inaccordance with device unit access frequencies, the control processor132 records the access frequency for each device unit. The CPU 111 ofthe management server 110 acquires information on the access frequencyand issues an instruction regarding the data repositioning in accordancewith an algorithm that is stored in the device migration instructionprocessing 242.

A case where the data repositioning is executed in file units ratherthan in device units will be described next. FIG. 21 shows an example ofan address conversion table 2100 that the management server 110comprises. The CPU 111 is able to create the address conversion table210 by acquiring information from the host computer. By using theaddress conversion table 210, the CPU 111 is able to read and write datain file units. Furthermore, this address conversion table is created foreach operating system.

FIG. 22 shows an example of the information that can be collected as aresult of the CPU 101 of the host computer 100 performing execution inaccordance with an instruction from the management server 110. The CPU101 of the host computer 100 collects the file name, file generationdate and time, final access date and time, file size, file address, andthe LU number of the storage destination, for each file. Aftercollecting these information items, the CPU 101 transmits same to themanagement server 110. The files that have not been accessed for a longtime can be subjected to data repositioning in accordance with the filegeneration date and time and final access date and time of thisinformation.

As a result of the configuration of the second embodiment, theassignment of the temporary area/permanent area of the nonvolatilememory can be changed dynamically in accordance with a systemconfiguration change and access characteristic change in addition to theeffects afforded by the first embodiment.

A few preferred embodiments of the present invention were describedhereinabove but these embodiments are illustrations serving to explainthe present invention, there being no intention to limit the scope ofthe present invention to these embodiments alone. The present inventioncan also be implemented in a variety of other forms.

For example, the present invention can also be applied to a mainframesystem instead of an open system.

Moreover, the functions of the management server 110 can be combinedwith those of the host computer 100, for example. In this case, themanagement server 110 is unnecessary and both the operation andmanagement can be implemented by the host computer. Furthermore, incases where the management server 110 issues instructions to the storagesystem 130, instructions can be executed by the management server 110 inan inbound direction via a fibre channel switch rather than in anoutbound direction via IP network 175.

For example, a NAS adapter can be built into the storage system. FIG. 23shows an example of a storage system with a built-in NAS adapter. Thedifference with respect to FIG. 1 is that the NAS adapter 2312 is builtinto the storage system 130 and that an IP switch 122 has been added.The processor 2311 of the NAS adapter 2310 is able to convert the fileaccess by the host computer into block access as a result of theoperating system or file system that is stored in the memory 2312 andsave the data in the nonvolatile memory 134, disks 137, and externalstorage systems 150. In cases where there is a built-in NAS adapter2310, file collection information 2200 is collected by the processor2311 and transmitted to the management server 110 via the managementterminal 140.

1. A storage system, comprising: a storage controller; a plurality offlash memory devices coupled to the storage controller, each of theflash memory devices including a flash memory controller and a pluralityof flash memory chips, being configured to be a logical volume forstoring data by the storage controller; and the storage controllerconfigured to: create a cache memory area using a first storage area ofthe plurality of flash memory devices for temporarily storing data; andcreate the logical volume using a second storage area of the pluralityof flash memory devices for storing data, the second storage area beingdifferent from the first storage area.